# AI-First Product Workshop: Preparation and Facilitator Guide ## TipTip and SatuSatu/Attractions Current date: Jul 27, 2026 Workshop date: Jul 30, 2026 Workshop time: 13:00-17:00 Location: TipTip Office @ GoWork Central Park # 1\. Workshop Agenda ## Objective Align business stakeholders on how TipTip and SatuSatu/Attractions can move from AI-assisted features toward AI-first product bets that improve revenue, differentiation, operating leverage, and investor appetite. ## Printed / Displayed Agenda | Time | Session | Output | | :---- | :---- | :---- | | 13:00-13:10 | Opening and workshop goals | Shared objective, working rules, and expected decisions. | | 13:10-13:35 | What AI-first means for TipTip | Agreed distinction between AI-assisted and AI-first, plus decision principles for evaluating ideas. | | 13:35-14:00 | Where we are today: AI already in TipTip | Current AI inventory, known use cases, limitations, and opportunity gaps. | | 14:00-14:10 | Break | Reset before group work. | | 14:10-15:30 | Journey-based ideation: TipTip and SatuSatu/Attractions | AI-first opportunities mapped against user journeys. | | 15:30-16:30 | Big bets prioritization | Top 3-5 AI-first product bets, ranked by business impact and feasibility. | | 16:30-17:00 | Wrap-up and next steps | Owners, follow-up artefacts, and 90-day validation plan. | # 2\. What Product Needs To Prepare ## Preparation Principles Keep preparation lightweight and decision-oriented. The goal is not to create a large research report. The goal is to give stakeholders enough shared context to make sharper product decisions in the room. ## Product Team Roles and Facilitation Responsibilities | Person | Role | Preparation Ownership | Workshop Facilitation Role | Notes / Decision Rights | | :---- | :---- | :---- | :---- | :---- | | Panji | CTPO | Frame AI-first ambition, investor narrative, technology/product direction, and decision boundaries. | Strategic sponsor; opens ambition and resolves trade-offs. | Keeps the AI-first bar high and aligns with company/investor narrative. | | Faisal | Head of Product | Own workshop design, prioritization criteria, facilitation flow, and final synthesis. | Lead facilitator; keeps flow, timing, and decision closure. | Accountable for final product bets and post-workshop synthesis. | | Dimas | Product Manager | Compile journeys, benchmarks, current AI usage, canvases, and participant inputs. | Synthesis owner and note taker; captures ideas, scores, decisions. | Turns workshop output into roadmap and big bet one-pagers. | | William | Product Designer | Prepare the workshop visual system | Co-facilitator for journey mapping and ideation; helps groups make ideas concrete. | Core co-facilitator for journey-based ideation and experience framing. | ## Preparation Timeline T-3: Alignment and participant pre-work kickoff Owner: Faisal with Panji, Dimas, and William Actions: * Confirm workshop objective, agenda, and expected decisions. * Align on scope: TipTip plus SatuSatu/Attractions. * Confirm participant list and roles. * Send email and WhatsApp message asking participants to read the pre-read, prepare problem hypotheses, and use Faisal's Google Form. * Assign benchmark research areas across product team members. Deliverables: * Final workshop agenda. * Participant pre-work email. * WhatsApp reminder message. * Research owner list. T-2: Benchmark research and pre-read drafting Owner: Dimas Actions: * Research global and SEA AI innovation benchmarks and reusable JTBD patterns. * Summarize AI-assisted vs AI-first patterns. * Collect current TipTip AI usage from internal teams. * Draft the protected Cloudflare Pages HTML pre-read. Deliverables: * Competitor benchmark table. * AI innovation pattern summary. * Draft pre-read material. * Draft problem-first workshop canvases. T-1: Final pre-read and facilitation pack Owner: Faisal and Dimas, reviewed by Panji; William prepares the workshop visuals and canvases. Actions: * Publish and circulate the protected Cloudflare Pages HTML pre-read. * Prepare printed/displayed agenda. * William prepares the current-state AI inventory, real-world problem capture, journey, AI opportunity, Big Bet, prioritization, and decision boards. * Assign facilitation roles: lead facilitator, timekeeper, note taker, and group leads. Deliverables: * Final protected HTML pre-read page. * Workshop facilitation guide. * Printed or digital canvases. * Prioritization scoring sheet. Workshop Day: Facilitate, decide, and capture output Owner: Faisal as lead facilitator, Panji as strategic sponsor, Dimas as synthesis owner, William as journey-mapping co-facilitator Actions: * Run each agenda block on time. * Capture decisions and unresolved questions. * Force ideas into clear product bets. * Align owners and next steps before closing. Deliverables: * Current AI inventory. * AI-first definition for TipTip and SatuSatu/Attractions. * Top 3-5 prioritized big bets. * 90-day validation plan. * Decision log. # 3\. Participant Communication ## 3.1 Email Subject: Required pre-work for AI-First Product Workshop Hi everyone, Workshop details: Jul 30, 2026, 13:00-17:00, TipTip Office @ GoWork Central Park. The workshop will align business stakeholders on what AI-first means for TipTip and SatuSatu/Attractions and which product bets should be validated next. Before the workshop, please: * Read the protected HTML pre-read in full so we start from the same baseline. * Research, observe, or dream from real-world problems that AI could address. * Bring 1-2 problem/opportunity hypotheses from your work, customers, partners, or market. * Use competitor examples as inspiration, not as a substitute for a real problem. * If possible, submit your ideas through the Google Form circulated by Faisal before the workshop. Prioritize problems that are: * Repetitive or high-volume. * Long-running or time-consuming. * Difficult to scale because resources or manpower are limited. * Dependent on manual judgment, handoffs, or specialist knowledge. For each idea, capture: * Who experiences the problem and in which journey or job-to-be-done. * How often it occurs or the approximate volume. * Time, manpower, delay, cost, or quality impact. * Current workaround and why it does not scale. * What AI could predict, recommend, generate, decide, automate, or optimize. * Desired user and business outcome. * Evidence or source link, if available. The product team will circulate the protected HTML pre-read page. Please read it before joining the workshop. **Appendix: Prompting Guide for own research** * [Anthropic: Claude prompting best practices](https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices) * [OpenAI: Reasoning best practices](https://developers.openai.com/api/docs/guides/reasoning-best-practices) * [Google Cloud: Prompt engineering overview and guide](https://cloud.google.com/discover/what-is-prompt-engineering?hl=en) Thanks, \[Name\] ## 3.2 WhatsApp Hi all, reminder for the AI-First Product Workshop on Jul 30, 2026, 13:00-17:00 at TipTip Office @ GoWork Central Park. Before the session, please read the protected HTML pre-read in full. Then bring 1-2 real-world problems that are repetitive, time-consuming, or difficult to scale because resources or manpower are limited. For each, note who has the problem, frequency/volume, time or manpower cost, current workaround, what AI could do, desired outcome, and any evidence or source. Competitor examples are welcome as inspiration. If possible, submit your ideas through the Google Form circulated by Faisal before the workshop. # 4\. Pre-Read Material ## Format and Hosting The pre-read should be an HTML page hosted on Cloudflare Pages and protected so only TipTip Google Workspace/Gmail accounts can access it. Keep it readable in 15-20 minutes. ## Access setup: * Host the page as a Cloudflare Pages project. * Protect it using Cloudflare Access with Google login. * Restrict access to TipTip company Gmail/Google Workspace accounts. * Share the protected URL in the participant email and WhatsApp reminder. ## Pre-Read Contents Outline 1\. AI innovations in competitor benchmarks: Global vs SEA Purpose: understand whether global market and SEA market show different AI adoption patterns. Content to include: * Global benchmarks from creator, community, event, travel, commerce, and AI-native products. * SEA benchmarks from relevant creator, commerce, community, travel, and attractions players. * For each benchmark: AI capability, target user, journey touched, AI-assisted vs AI-first classification, commercial impact, and source link. * A short comparison of what looks different between global and SEA markets. 2\. Remap AI innovations to JTBD Purpose: identify common use cases that can become quick wins for TipTip and SatuSatu/Attractions. Content to include: * Map each benchmarked AI innovation to the user job-to-be-done and problem pattern it addresses. * Cluster repeated jobs across creators, communities, event organizers, travelers, and attractions partners. * Highlight common use cases that appear across multiple competitors. * Mark which use cases look like quick wins, strategic bets, or low-priority ideas. 3\. SWOT and Product Recommendation Purpose: give stakeholders a clear product-team point of view before the workshop. Content to include: * Strengths: current assets, data, workflows, or distribution TipTip can build on. * Weaknesses: product, data, operational, or technical gaps that limit AI-first execution. * Opportunities: AI-first product bets that could improve revenue, conversion, retention, supply quality, or investor narrative. * Threats: competitor, platform, data, or execution risks. * Product recommendation: 3-5 recommended AI-first opportunity areas, expected value, dependencies, and key assumptions to pressure-test during the workshop. # 5\. Facilitator Guide During Workshop Use this table as the live run sheet. Faisal owns timing and decision closure; Dimas captures decisions and evidence; William co-facilitates journey work; Panji sets the strategic bar and resolves trade-offs. | Time | Session / lead | Facilitator moves | Prompt / required output | | :---- | :---- | :---- | :---- | | **13:00-13:10** | **Opening and goals Lead:** Faisal \+ Panji | Panji frames the ambition and business context. Faisal states the decisions required by 17:00, confirms facilitation roles, and sets working rules: start from observed problems and evidence, anchor on user journeys, separate facts from assumptions, connect ideas to business impact, and keep one conversation at a time. | **Prompt:** Which AI-first bets should we validate next, who owns each, and what proof is needed within 90 days? **Output:** shared objective, decision rules, and expected artefacts. **Time gate:** close at 13:10. | | **13:10-13:35** | **What AI-first means Lead:** Faisal \+ Dimas | Start with the proposed distinction. Give 3 minutes for silent reactions, 10 minutes to challenge and refine it, 7 minutes to agree one-sentence definitions for each product, and 5 minutes to confirm the evaluation principles. | **Starting point:** AI-assisted improves an existing task; AI-first changes the core workflow and learns or acts toward an outcome. **Test:** journey change; measurable value; proprietary data loop; 90-day validation; credible investor story. **Output:** definitions for TipTip and SatuSatu/Attractions plus four decision principles. | | **13:35-14:00** | **Current AI baseline Lead:** Dimas \+ William | Use 5 minutes for individual capture, 8 minutes for round-robin, 7 minutes for clustering, and 5 minutes for AI-assisted vs AI-first classification. Dimas records evidence and gaps, not only feature names. | **Prompts: Who benefits? What outcome changes? What evidence supports it? What limitation remains? Could AI own more of the outcome?** **Canvas: product area; current AI use; impact; evidence; limitation; AI-first opportunity.** **Output:** current AI inventory and 3-5 opportunity themes. | | **14:00-14:10** | **Break Lead:** Dimas \+ William | Ask everyone to return by 14:10. During the break, Dimas and William organize the first-hour notes into 3-5 visible themes and prepare the journey boards. | **Output:** clean boards and named themes ready for group work. **Time gate:** restart at 14:10. | | **14:10-15:30** | **Journey-based ideation Lead:** Dimas \+ William | Assign 2-3 groups to the creator, event/community, and SatuSatu traveler/partner journeys. Spend 5 minutes on instructions, 15 minutes mapping friction, 25 minutes generating possibilities, 20 minutes selecting the top three, and 15 minutes on share-outs (5 minutes per group). | **Prompts: Where is work repetitive, long-running, or constrained by manpower? Who experiences it, how often, and what is the current workaround? What should AI predict, recommend, generate, decide, automate, or optimize?** **Canvas: journey step; actor; friction; frequency/volume; time/manpower cost; current workaround; evidence; AI behavior; data/input; user trust/control; desired outcome; idea.** **Output:** top three AI-first ideas per group. **Only if groups stall,** seed with Creator Growth OS, Event Commerce Engine, Travel Concierge, or Partner Yield Optimizer. | | **15:30-16:30** | **Big bets prioritization Lead:** Faisal \+ Dimas; Panji resolves trade-offs | Cluster and merge ideas for 10 minutes. Complete big-bet cards for 15 minutes. Score individually for 15 minutes. Discuss scoring gaps and trade-offs for 15 minutes. Use the final 5 minutes to confirm the shortlist; do not make every idea a priority. | **Big-bet card: target user; problem evidence; AI-first behavior; why not merely assisted; business impact; data advantage; dependencies; 90-day test; owner; success metric; reject/defer trigger.** **Score 1-5:** customer/business impact (40%); AI/data defensibility (25%); 90-day feasibility (20%); investor narrative clarity (15%). **Output:** ranked top 3-5 bets and reasons for rejection or deferral. | | **16:30-17:00** | **Decisions and next steps Lead:** Faisal \+ Dimas | Read back the ranked bets for 5 minutes. Assign one accountable owner and validation question per bet for 10 minutes. Define the 90-day experiment, required evidence, and success metric for 10 minutes. Use the last 5 minutes to confirm the next review date and parking-lot items. | **Output:** final 3-5 bets; owner per bet; 90-day validation plan; success metrics; decision log; unresolved dependencies; synthesis-sharing date. **Decision rule:** Panji closes unresolved strategic trade-offs after hearing the score and evidence. | # 6\. Post-Workshop Artefacts Product should produce the following after the workshop: **1\. Workshop synthesis** * Summary of discussion. * Final AI-first definitions. * Key themes from current AI inventory. * Prioritized big bets. **2\. Big bet one-pagers** For each selected bet: * Problem. * Target user. * Proposed AI-first experience. * Business impact. * Data advantage. * MVP scope. * Risks and dependencies. * Owner. * Success metric. **3\. 90-day roadmap** * What will be validated. * What prototype or experiment will be built. * What data is needed. * Which team owns execution. * What decision will be made after validation. **4\. Investor narrative draft** TipTip is evolving into an AI-first creator growth operating system that uses creator, audience, event, and transaction data to help creators grow and optimize revenue. SatuSatu/Attractions is evolving into an AI-first orchestration platform that uses traveler, inventory, partner, and transaction data to personalize discovery, bundle experiences, and optimize demand. **5\. Decision log** * What was agreed. * What was rejected. * What needs more validation. * Owner and timeline for each follow-up.